..Sort of resolves #9195 as well.

It is a start on it, following that functionality in M600. Just took a glance at that and it seems pretty easy to do using things we have in place now.

@InsanityAutomation — Please delete your dead branches!

@InsanityAutomation — Please delete your dead branches!

I actually don't have that many dead ones, I think there's only one or two to remove! With 70 machines, most of them different models you end up with a lot of different branches...

I think there's only one or two to remove

The problem is not purely the number of branches, but that there are a lot of dead or dangling references that are no longer in the upstream repo or our working copies, so if you cannot delete them then you have a couple of options to make things friendlier for us:

• You could rebase them on some tagged version of Marlin, either in the 2.0.x branch or the bugfix-2.0.x branch, and then push the rebased branches. This way git fetch will only need to pull down the references that it doesn't yet have.

• Another perfectly good option is to create a new repository separate from the one you use to submit upstream changes, reset it to be a clone of upstream Marlin and/or do a git remote add of MarlinFirmware/Marlin for convenience, and move your 70 machine-specific branches there. Then you can delete them from the repository that you use for submitting PRs.